Building automation systems with automatic metadata tagging

ABSTRACT

A method for tagging entities in a building automation system (BAS), the method including identifying, by a processing circuit, a first entity of one or more entities in a system library in response to receiving an indication to add the one or more entities to the BAS, wherein the system library includes a number of relationships between a number of tags and a number of entities. The method further including determining, by the processing circuit, one or more tags associated with the first entity based on the system library, determining, by the processing circuit, a tag type for each of the one or more tags based on a tag dictionary, and adding, by the processing circuit, the one or more tags to the first entity based on the tag type of each of the one or more tags.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional. PatentApplication No. 62/625,101 filed on Feb. 1, 2018, entitled: “BuildingAutomation Systems with Automatic Metadata Tagging,” the entire contentsof which are hereby incorporated by reference herein.

BACKGROUND

The present disclosure relates generally to a building management system(BMS) and more particularly to classifying entities within a BMS usingmetadata tagging.

A building management system (BMS) is, in general, a system of devicesconfigured to control, monitor, and manage equipment in or around abuilding or building area. A BMS can include a heating, ventilation, andair conditioning (HVAC) system, a security system, a lighting system, afire alerting system, another system that is capable of managingbuilding functions or devices, or any combination thereof. BMS devicescan be installed in any environment (e.g., an indoor area or an outdoorarea) and the environment can include any number of buildings, spaces,zones, rooms, or areas. A BMS can include a variety of devices (e.g.,HVAC devices, controllers, chillers, fans, sensors, etc.) configured tofacilitate monitoring and controlling the building space. Throughoutthis disclosure, such devices are referred to as BMS devices or buildingequipment.

Advanced building management system applications sometimes rely on theclassification and identification of points, devices, and entities. Forexample, tagging may be a valuable mechanism for associating metadatawith BMS entities in a station. Herein, the term “station” refers to aninstance of relevant software, which can run on a variety of hardwareplatforms. Some tagging applications allow a tag to be associated withan entity, either manually (“direct tags”) or automatically (“impliedtags”).

The process of using direct tags generally requires several steps. Forexample, for each entity, a menu item is selected. Then a tag dictionaryis selected, and from there the user selects the appropriate direct tagor tag group. The tag is added at any time after the entity is added tothe station. This process can be tedious and time-consuming.

Implementing implied tags generally involves the use of a tagdictionary, which contains rules that add implied tags depending on theevaluation of that rule. This evaluation generally occurs when theentity is added to the station. This method requires sophisticatedconstruction of the tag dictionary, and the user may lack control overwhich tags are added to an entity.

SUMMARY

One implementation of the present disclosure is a method for taggingentities in a building automation system (BAS), the method includingidentifying, by a processing circuit, a first entity of one or moreentities in a system library in response to receiving an indication toadd the one or more entities to the BAS system, wherein the systemlibrary includes a number of relationships between a number of tags anda number of entities. The method further including determining, by theprocessing circuit, one or more tags associated with the first entitybased on the system library, determining, by the processing circuit, atag type for each of the one or more tags based on a tag dictionary, andadding, by the processing circuit, the one or more tags to the firstentity based on the tag type of each of the one or more tags.

In some embodiments the method further includes verifying the one ormore tags, wherein verifying the one or more tags includes comparing theone or more tags to the number of tags in the system library. In someembodiments the processing circuit omits adding duplicate tags to thefirst entity based on the comparison. In some embodiments a userinterface produces the indication to add the one or more entities to theBAS system. In some embodiments the first entity includes one of aspace, a piece of equipment, a sensor, a device, or a point. In someembodiments the tag type is a value tag, wherein a value tag furtherincludes a numeric value associated with the first entity. In someembodiments the method further includes adding, by the processingcircuit, the numeric value to the first entity.

Another implementation of the present disclosure is a method forconverting tag syntax in a building management system (BMS), the methodincluding receiving, by a processing circuit, a first tag correspondingto a first entity and having a first syntax, identifying, by theprocessing circuit, a system library associated with the first entity,wherein the system library includes a number of relationships between anumber of tags and a number of entities. The method further includesinitiating, by the processing circuit, an update process, the processincluding building one or more second tags corresponding to the firstentity and having a second syntax.

In some embodiments building the one or more second tags includesdetermining one or more second tags associated with the first entitybased on the system library, determining a tag type for each of the oneor more second tags based on a tag dictionary, and adding the one ormore second tags to the first entity based on a tag type of each of theone or more second tags. In some embodiments the method further includesverifying the one or more second tags, wherein verifying the one or moresecond tags includes comparing the one or more second tags to the numberof tags in the system library. In some embodiments duplicate tags areomitted from addition to the first entity based on the comparison. Insome embodiments the first entity includes one of a space, a piece ofequipment, a sensor, a device, or a point. In some embodiments the tagtype is a value tag, wherein a value tag further includes a numericvalue associated with the first entity. In some embodiments the methodfurther includes adding, by the processing circuit, the numeric value tothe first entity.

Another implementation of the present disclosure is a buildingautomation system (BAS) including a system library including a number ofrelationships between a number of tags and a number of entities. The BASfurther includes a computing system coupled to the system libraryconfigured to perform a first import process and a second updateprocess, wherein the first import process associates one or more tagswith a first entity, and wherein the second update process updates afirst tag associated with a second entity by building one or more secondtags.

In some embodiments the first import process includes identifying thefirst entity in the system library, determining the one or more tagsassociated with the first entity based on the system library,determining a tag type for each of the one or more tags based on a tagdictionary, and adding the one or more tags to the first entity based onthe tag type of each of the one or more tags. In some embodiments thesecond update process includes receiving the first tag corresponding tothe second entity and having a first syntax, identifying a system typeassociated with the second entity, wherein the system type is associatedwith the number of relationships in the system library, and building oneor more second tags corresponding to the second entity and having asecond syntax. In some embodiments, building the one or more second tagsincludes determining the one or more second tags associated with thesecond entity based on the system library, determining a tag type foreach of the one or more second tags based on a tag dictionary, andadding the one or more second tags to the second entity based on the tagtype of each of the one or more second tags. In some embodiments the tagtype is a value tag, wherein a value tag further includes a numericvalue associated with the second entity. In some embodiments the firstentity includes one of a space, a piece of equipment, a sensor, adevice, or a point.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, accordingto some embodiments.

FIG. 2 is a block diagram of a waterside system which can be used toserve the building of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be used toserve the building of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a building management system (BMS) whichcan be used to monitor and control the building of FIG. 1, according tosome embodiments.

FIG. 5 is a block diagram of another building management system whichcan be used to monitor and control the building and HVAC system of FIG.1, according to some embodiments.

FIG. 6 is a block diagram of a controller which can be used in a BMS,according to some embodiments.

FIG. 7 is a flowchart of a method for tagging devices and/or points,according to some embodiments.

FIG. 8 is a flowchart of a method for tagging devices and/or points,according to some embodiments.

FIG. 9 is a flowchart of a method for tagging devices and/or points uponimport, according to some embodiments.

FIG. 10 is a flowchart of a method for updating device and/or pointtags, according to some embodiments.

FIG. 11 is an image of an example interface for automatic tagging ofdevices, according to some embodiments.

FIG. 12 is an image of an example interface for editing a systemlibrary, according to some embodiments.

FIG. 13 is an image of an example interface for editing points within asystem library, according to some embodiments.

FIG. 14 is an image of an example interface for converting tag format,according to some embodiments.

DETAILED DESCRIPTION

Before turning to the Figures, it should be understood that thedisclosure is not limited to the details or methodology set forth in thedescription or illustrated in the figures. It should also be understoodthat the terminology is for the purpose of description only and shouldnot be regarded as limiting.

Referring generally to the Figures, a computing system for automaticallytagging entities in a building automation system (BMS) is shown anddescribed. The computing system may be utilized in conjunction with aplurality of building automation or management systems, subsystems, oras a part high level building automation system. For example, thecomputer system may be a part of a Johnson Controls Facility Explorersystem. Devices and control points are central to many buildingmanagement systems, as well as to the construction of a station.Accordingly, the present disclosure emphasizes devices and controlpoints (“points”) when automatically adding tags.

The present disclosure describes systems and methods that address theshortcomings of conventional systems. For example, embodiments of thecomputing system disclosed herein can be configured to combine theflexibility of direct tagging techniques with the efficiency of impliedtagging techniques. Accordingly, embodiments of the present disclosuredescribes several mechanisms for tags to be added automatically, alongwith ways for users to conveniently modify which tags are added bydefault. Furthermore, embodiments of the systems and methods disclosedherein describe techniques for facilitating use of tags in multiplesoftware platforms, for example by converting previously-created tags toa format compatible with other software platforms.

Building HVAC Systems and Building Management Systems

Referring now to FIGS. 1-5, several building management systems (BMS)and HVAC systems in which the systems and methods of the presentdisclosure can be implemented are shown, according to some embodiments.In brief overview, FIG. 1 shows a building 10 equipped with a HVACsystem 100. FIG. 2 is a block diagram of a waterside system 200 whichcan be used to serve building 10. FIG. 3 is a block diagram of anairside system 300 which can be used to serve building 10. FIG. 4 is ablock diagram of a BMS which can be used to monitor and control building10. FIG. 5 is a block diagram of another BMS which can be used tomonitor and control building 10.

Building and HVAC System

Referring particularly to FIG. 1, a perspective view of a building 10 isshown. Building 10 is served by a BMS. A BMS is, in general, a system ofdevices configured to control, monitor, and manage equipment in oraround a building or building area. A BMS can include, for example, aHVAC system, a security system, a lighting system, a fire alertingsystem, and any other system that is capable of managing buildingfunctions or devices, or any combination thereof.

The BMS that serves building 10 includes a HVAC system 100. HVAC system100 can include a plurality of HVAC devices (e.g., heaters, chillers,air handling units, pumps, fans, thermal energy storage, etc.)configured to provide heating, cooling, ventilation, or other servicesfor building 10. For example, HVAC system 100 is shown to include awaterside system 120 and an airside system 130. Waterside system 120 mayprovide a heated or chilled fluid to an air handling unit of airsidesystem 130. Airside system 130 may use the heated or chilled fluid toheat or cool an airflow provided to building 10. An exemplary watersidesystem and airside system which can be used in HVAC system 100 aredescribed in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and arooftop air handling unit (AHU) 106. Waterside system 120 may use boiler104 and chiller 102 to heat or cool a working fluid (e.g., water,glycol, etc.) and may circulate the working fluid to AHU 106. In variousembodiments, the HVAC devices of waterside system 120 can be located inor around building 10 (as shown in FIG. 1) or at an offsite locationsuch as a central plant (e.g., a chiller plant, a steam plant, a heatplant, etc.). The working fluid can be heated in boiler 104 or cooled inchiller 102, depending on whether heating or cooling is required inbuilding 10. Boiler 104 may add heat to the circulated fluid, forexample, by burning a combustible material (e.g., natural gas) or usingan electric heating element. Chiller 102 may place the circulated fluidin a heat exchange relationship with another fluid (e.g., a refrigerant)in a heat exchanger (e.g., an evaporator) to absorb heat from thecirculated fluid. The working fluid from chiller 102 and/or boiler 104can be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship withan airflow passing through AHU 106 (e.g., via one or more stages ofcooling coils and/or heating coils). The airflow can be, for example,outside air, return air from within building 10, or a combination ofboth. AHU 106 may transfer heat between the airflow and the workingfluid to provide heating or cooling for the airflow. For example, AHU106 can include one or more fans or blowers configured to pass theairflow over or through a heat exchanger containing the working fluid.The working fluid may then return to chiller 102 or boiler 104 viapiping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e.,the supply airflow) to building 10 via air supply ducts 112 and mayprovide return air from building 10 to AHU 106 via air return ducts 114.In some embodiments, airside system 130 includes multiple variable airvolume (VAV) units 116. For example, airside system 130 is shown toinclude a separate VAV unit 116 on each floor or zone of building 10.VAV units 116 can include dampers or other flow control elements thatcan be operated to control an amount of the supply airflow provided toindividual zones of building 10. In other embodiments, airside system130 delivers the supply airflow into one or more zones of building 10(e.g., via supply ducts 112) without using intermediate VAV units 116 orother flow control elements. AHU 106 can include various sensors (e.g.,temperature sensors, pressure sensors, etc.) configured to measureattributes of the supply airflow. AHU 106 may receive input from sensorslocated within AHU 106 and/or within the building zone and may adjustthe flow rate, temperature, or other attributes of the supply airflowthrough AHU 106 to achieve setpoint conditions for the building zone.

Waterside System

Referring now to FIG. 2, a block diagram of a waterside system 200 isshown, according to some embodiments. In various embodiments, watersidesystem 200 may supplement or replace waterside system 120 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, waterside system 200 can include asubset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller102, pumps, valves, etc.) and may operate to supply a heated or chilledfluid to AHU 106. The HVAC devices of waterside system 200 can belocated within building 10 (e.g., as components of waterside system 120)or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having aplurality of subplants 202-212. Subplants 202-212 are shown to include aheater subplant 202, a heat recovery chiller subplant 204, a chillersubplant 206, a cooling tower subplant 208, a hot thermal energy storage(TES) subplant 210, and a cold thermal energy storage (TES) subplant212. Subplants 202-212 consume resources (e.g., water, natural gas,electricity, etc.) from utilities to serve thermal energy loads (e.g.,hot water, cold water, heating, cooling, etc.) of a building or campus.For example, heater subplant 202 can be configured to heat water in ahot water loop 214 that circulates the hot water between heater subplant202 and building 10. Chiller subplant 206 can be configured to chillwater in a cold water loop 216 that circulates the cold water betweenchiller subplant 206 and building 10. Heat recovery chiller subplant 204can be configured to transfer heat from cold water loop 216 to hot waterloop 214 to provide additional heating for the hot water and additionalcooling for the cold water. Condenser water loop 218 may absorb heatfrom the cold water in chiller subplant 206 and reject the absorbed heatin cooling tower subplant 208 or transfer the absorbed heat to hot waterloop 214. Hot TES subplant 210 and cold TES subplant 212 may store hotand cold thermal energy, respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/orchilled water to air handlers located on the rooftop of building 10(e.g., AHU 106) or to individual floors or zones of building 10 (e.g.,VAV units 116). The air handlers push air past heat exchangers (e.g.,heating coils or cooling coils) through which the water flows to provideheating or cooling for the air. The heated or cooled air can bedelivered to individual zones of building 10 to serve thermal energyloads of building 10. The water then returns to subplants 202-212 toreceive further heating or cooling.

Although subplants 202-212 are shown and described as heating andcooling water for circulation to a building, it is understood that anyother type of working fluid (e.g., glycol, CO2, etc.) can be used inplace of or in addition to water to serve thermal energy loads. In otherembodiments, subplants 202-212 may provide heating and/or coolingdirectly to the building or campus without requiring an intermediateheat transfer fluid. These and other variations to waterside system 200are within the teachings of the present disclosure.

Each of subplants 202-212 can include a variety of equipment configuredto facilitate the functions of the subplant. For example, heatersubplant 202 is shown to include a plurality of heating elements 220(e.g., boilers, electric heaters, etc.) configured to add heat to thehot water in hot water loop 214. Heater subplant 202 is also shown toinclude several pumps 222 and 224 configured to circulate the hot waterin hot water loop 214 and to control the flow rate of the hot waterthrough individual heating elements 220. Chiller subplant 206 is shownto include a plurality of chillers 232 configured to remove heat fromthe cold water in cold water loop 216. Chiller subplant 206 is alsoshown to include several pumps 234 and 236 configured to circulate thecold water in cold water loop 216 and to control the flow rate of thecold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality ofheat recovery heat exchangers 226 (e.g., refrigeration circuits)configured to transfer heat from cold water loop 216 to hot water loop214. Heat recovery chiller subplant 204 is also shown to include severalpumps 228 and 230 configured to circulate the hot water and/or coldwater through heat recovery heat exchangers 226 and to control the flowrate of the water through individual heat recovery heat exchangers 226.Cooling tower subplant 208 is shown to include a plurality of coolingtowers 238 configured to remove heat from the condenser water incondenser water loop 218. Cooling tower subplant 208 is also shown toinclude several pumps 240 configured to circulate the condenser water incondenser water loop 218 and to control the flow rate of the condenserwater through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configuredto store the hot water for later use. Hot TES subplant 210 may alsoinclude one or more pumps or valves configured to control the flow rateof the hot water into or out of hot TES tank 242. Cold TES subplant 212is shown to include cold TES tanks 244 configured to store the coldwater for later use. Cold TES subplant 212 may also include one or morepumps or valves configured to control the flow rate of the cold waterinto or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200(e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines inwaterside system 200 include an isolation valve associated therewith.Isolation valves can be integrated with the pumps or positioned upstreamor downstream of the pumps to control the fluid flows in watersidesystem 200. In various embodiments, waterside system 200 can includemore, fewer, or different types of devices and/or subplants based on theparticular configuration of waterside system 200 and the types of loadsserved by waterside system 200.

Airside System

Referring now to FIG. 3, a block diagram of an airside system 300 isshown, according to some embodiments. In various embodiments, airsidesystem 300 may supplement or replace airside system 130 in HVAC system100 or can be implemented separate from HVAC system 100. Whenimplemented in HVAC system 100, airside system 300 can include a subsetof the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116,ducts 112-114, fans, dampers, etc.) and can be located in or aroundbuilding 10. Airside system 300 may operate to heat or cool an airflowprovided to building 10 using a heated or chilled fluid provided bywaterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type airhandling unit (AHU) 302. Economizer-type AHUs vary the amount of outsideair and return air used by the air handling unit for heating or cooling.For example, AHU 302 may receive return air 304 from building zone 306via return air duct 308 and may deliver supply air 310 to building zone306 via supply air duct 312. In some embodiments, AHU 302 is a rooftopunit located on the roof of building 10 (e.g., AHU 106 as shown inFIG. 1) or otherwise positioned to receive both return air 304 andoutside air 314. AHU 302 can be configured to operate exhaust air damper316, mixing damper 318, and outside air damper 320 to control an amountof outside air 314 and return air 304 that combine to form supply air310. Any return air 304 that does not pass through mixing damper 318 canbe exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example,exhaust air damper 316 can be operated by actuator 324, mixing damper318 can be operated by actuator 326, and outside air damper 320 can beoperated by actuator 328. Actuators 324-328 may communicate with an AHUcontroller 330 via a communications link 332. Actuators 324-328 mayreceive control signals from AHU controller 330 and may provide feedbacksignals to AHU controller 330. Feedback signals can include, forexample, an indication of a current actuator or damper position, anamount of torque or force exerted by the actuator, diagnosticinformation (e.g., results of diagnostic tests performed by actuators324-328), status information, commissioning information, configurationsettings, calibration data, and/or other types of information or datathat can be collected, stored, or used by actuators 324-328. AHUcontroller 330 can be an economizer controller configured to use one ormore control algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil334, a heating coil 336, and a fan 338 positioned within supply air duct312. Fan 338 can be configured to force supply air 310 through coolingcoil 334 and/or heating coil 336 and provide supply air 310 to buildingzone 306. AHU controller 330 may communicate with fan 338 viacommunications link 340 to control a flow rate of supply air 310. Insome embodiments, AHU controller 330 controls an amount of heating orcooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200(e.g., from cold water loop 216) via piping 342 and may return thechilled fluid to waterside system 200 via piping 344. Valve 346 can bepositioned along piping 342 or piping 344 to control a flow rate of thechilled fluid through cooling coil 334. In some embodiments, coolingcoil 334 includes multiple stages of cooling coils that can beindependently activated and deactivated (e.g., by AHU controller 330, byBMS controller 366, etc.) to modulate an amount of cooling applied tosupply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and may return the heatedfluid to waterside system 200 via piping 350. Valve 352 can bepositioned along piping 348 or piping 350 to control a flow rate of theheated fluid through heating coil 336. In some embodiments, heating coil336 includes multiple stages of heating coils that can be independentlyactivated and deactivated (e.g., by AHU controller 330, by BMScontroller 366, etc.) to modulate an amount of heating applied to supplyair 310.

Each of valves 346 and 352 can be controlled by an actuator. Forexample, valve 346 can be controlled by actuator 354 and valve 352 canbe controlled by actuator 356. Actuators 354-356 may communicate withAHU controller 330 via communications links 358-360. Actuators 354-356may receive control signals from AHU controller 330 and may providefeedback signals to controller 330. In some embodiments, AHU controller330 receives a measurement of the supply air temperature from atemperature sensor 362 positioned in supply air duct 312 (e.g.,downstream of cooling coil 334 and/or heating coil 336). AHU controller330 may also receive a measurement of the temperature of building zone306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 viaactuators 354-356 to modulate an amount of heating or cooling providedto supply air 310 (e.g., to achieve a setpoint temperature for supplyair 310 or to maintain the temperature of supply air 310 within asetpoint temperature range). The positions of valves 346 and 352 affectthe amount of heating or cooling provided to supply air 310 by coolingcoil 334 or heating coil 336 and may correlate with the amount of energyconsumed to achieve a desired supply air temperature. AHU 330 maycontrol the temperature of supply air 310 and/or building zone 306 byactivating or deactivating coils 334-336, adjusting a speed of fan 338,or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include abuilding management system (BMS) controller 366 and a client device 368.BMS controller 366 can include one or more computer systems (e.g.,servers, supervisory controllers, subsystem controllers, etc.) thatserve as system level controllers, application or data servers, headnodes, or master controllers for airside system 300, waterside system200, HVAC system 100, and/or other controllable systems that servebuilding 10. BMS controller 366 may communicate with multiple downstreambuilding systems or subsystems (e.g., HVAC system 100, a securitysystem, a lighting system, waterside system 200, etc.) via acommunications link 370 according to like or disparate protocols (e.g.,LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMScontroller 366 can be separate (as shown in FIG. 3) or integrated. In anintegrated implementation, AHU controller 330 can be a software moduleconfigured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMScontroller 366 (e.g., commands, setpoints, operating boundaries, etc.)and provides information to BMS controller 366 (e.g., temperaturemeasurements, valve or actuator positions, operating statuses,diagnostics, etc.). For example, AHU controller 330 may provide BMScontroller 366 with temperature measurements from temperature sensors362-364, equipment on/off states, equipment operating capacities, and/orany other information that can be used by BMS controller 366 to monitoror control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces orclient interfaces (e.g., graphical user interfaces, reportinginterfaces, text-based computer interfaces, client-facing web services,web servers that provide pages to web clients, etc.) for controlling,viewing, or otherwise interacting with HVAC system 100, its subsystems,and/or devices. Client device 368 can be a computer workstation, aclient terminal, a remote or local interface, or any other type of userinterface device. Client device 368 can be a stationary terminal or amobile device. For example, client device 368 can be a desktop computer,a computer server with a user interface, a laptop computer, a tablet, asmartphone, a PDA, or any other type of mobile or non-mobile device.Client device 368 may communicate with BMS controller 366 and/or AHUcontroller 330 via communications link 372.

Building Management Systems

Referring now to FIG. 4, a block diagram of a building management system(BMS) 400 is shown, according to some embodiments. BMS 400 can beimplemented in building 10 to automatically monitor and control variousbuilding functions. BMS 400 is shown to include BMS controller 366 and aplurality of building subsystems 428. Building subsystems 428 are shownto include a building electrical subsystem 434, an informationcommunication technology (ICT) subsystem 436, a security subsystem 438,a HVAC subsystem 440, a lighting subsystem 442, a lift/escalatorssubsystem 432, and a fire safety subsystem 430. In various embodiments,building subsystems 428 can include fewer, additional, or alternativesubsystems. For example, building subsystems 428 may also oralternatively include a refrigeration subsystem, an advertising orsignage subsystem, a cooking subsystem, a vending subsystem, a printeror copy service subsystem, or any other type of building subsystem thatuses controllable equipment and/or sensors to monitor or controlbuilding 10. In some embodiments, building subsystems 428 includewaterside system 200 and/or airside system 300, as described withreference to FIGS. 2-3.

Each of building subsystems 428 can include any number of devices,controllers, and connections for completing its individual functions andcontrol activities. HVAC subsystem 440 can include many of the samecomponents as HVAC system 100, as described with reference to FIGS. 1-3.For example, HVAC subsystem 440 can include a chiller, a boiler, anynumber of air handling units, economizers, field controllers,supervisory controllers, actuators, temperature sensors, and otherdevices for controlling the temperature, humidity, airflow, or othervariable conditions within building 10. Lighting subsystem 442 caninclude any number of light fixtures, ballasts, lighting sensors,dimmers, or other devices configured to controllably adjust the amountof light provided to a building space. Security subsystem 438 caninclude occupancy sensors, video surveillance cameras, digital videorecorders, video processing servers, intrusion detection devices, accesscontrol devices and servers, or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include acommunications interface 407 and a BMS interface 409. Interface 407 mayfacilitate communications between BMS controller 366 and externalapplications (e.g., monitoring and reporting applications 422,enterprise control applications 426, remote systems and applications444, applications residing on client devices 448, etc.) for allowinguser control, monitoring, and adjustment to BMS controller 366 and/orsubsystems 428. Interface 407 may also facilitate communications betweenBMS controller 366 and client devices 448. BMS interface 409 mayfacilitate communications between BMS controller 366 and buildingsubsystems 428 (e.g., HVAC, lighting security, lifts, powerdistribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communicationsinterfaces (e.g., jacks, antennas, transmitters, receivers,transceivers, wire terminals, etc.) for conducting data communicationswith building subsystems 428 or other external systems or devices. Invarious embodiments, communications via interfaces 407, 409 can bedirect (e.g., local wired or wireless communications) or via acommunications network 446 (e.g., a WAN, the Internet, a cellularnetwork, etc.). For example, interfaces 407, 409 can include an Ethernetcard and port for sending and receiving data via an Ethernet-basedcommunications link or network. In another example, interfaces 407, 409can include a Wi-Fi transceiver for communicating via a wirelesscommunications network. In another example, one or both of interfaces407, 409 can include cellular or mobile phone communicationstransceivers. In one embodiment, communications interface 407 is a powerline communications interface and BMS interface 409 is an Ethernetinterface. In other embodiments, both communications interface 407 andBMS interface 409 are Ethernet interfaces or are the same Ethernetinterface.

Still referring to FIG. 4, BMS controller 366 is shown to include aprocessing circuit 404 including a processor 406 and memory 408.Processing circuit 404 can be communicably connected to BMS interface409 and/or communications interface 407 such that processing circuit 404and the various components thereof can send and receive data viainterfaces 407, 409. Processor 406 can be implemented as a generalpurpose processor, an application specific integrated circuit (ASIC),one or more field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can includeone or more devices (e.g., RAM, ROM, Flash memory, hard disk storage,etc.) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent application. Memory 408 can be or include volatile memory ornon-volatile memory. Memory 408 can include database components, objectcode components, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present application. According to someembodiments, memory 408 is communicably connected to processor 406 viaprocessing circuit 404 and includes computer code for executing (e.g.,by processing circuit 404 and/or processor 406) one or more processesdescribed herein.

In some embodiments, BMS controller 366 is implemented within a singlecomputer (e.g., one server, one housing, etc.). In various otherembodiments BMS controller 366 can be distributed across multipleservers or computers (e.g., that can exist in distributed locations).Further, while FIG. 4 shows applications 422 and 426 as existing outsideof BMS controller 366, in some embodiments, applications 422 and 426 canbe hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterpriseintegration layer 410, an automated measurement and validation (AM&V)layer 412, a demand response (DR) layer 414, a fault detection anddiagnostics (FDD) layer 416, an integrated control layer 418, and abuilding subsystem integration later 420. Layers 410-420 can beconfigured to receive inputs from building subsystems 428 and other datasources, determine optimal control actions for building subsystems 428based on the inputs, generate control signals based on the optimalcontrol actions, and provide the generated control signals to buildingsubsystems 428. The following paragraphs describe some of the generalfunctions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients orlocal applications with information and services to support a variety ofenterprise-level applications. For example, enterprise controlapplications 426 can be configured to provide subsystem-spanning controlto a graphical user interface (GUI) or to any number of enterprise-levelbusiness applications (e.g., accounting systems, user identificationsystems, etc.). Enterprise control applications 426 may also oralternatively be configured to provide configuration GUIs forconfiguring BMS controller 366. In yet other embodiments, enterprisecontrol applications 426 can work with layers 410-420 to optimizebuilding performance (e.g., efficiency, energy use, comfort, or safety)based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to managecommunications between BMS controller 366 and building subsystems 428.For example, building subsystem integration layer 420 may receive sensordata and input signals from building subsystems 428 and provide outputdata and control signals to building subsystems 428. Building subsystemintegration layer 420 may also be configured to manage communicationsbetween building subsystems 428. Building subsystem integration layer420 translates communications (e.g., sensor data, input signals, outputsignals, etc.) across a plurality of multi-vendor/multi-protocolsystems.

Demand response layer 414 can be configured to optimize resource usage(e.g., electricity use, natural gas use, water use, etc.) and/or themonetary cost of such resource usage in response to satisfy the demandof building 10. The optimization can be based on time-of-use prices,curtailment signals, energy availability, or other data received fromutility providers, distributed energy generation systems 424, fromenergy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or fromother sources. Demand response layer 414 may receive inputs from otherlayers of BMS controller 366 (e.g., building subsystem integration layer420, integrated control layer 418, etc.). The inputs received from otherlayers can include environmental or sensor inputs such as temperature,carbon dioxide levels, relative humidity levels, air quality sensoroutputs, occupancy sensor outputs, room schedules, and the like. Theinputs may also include inputs such as electrical use (e.g., expressedin kWh), thermal load measurements, pricing information, projectedpricing, smoothed pricing, curtailment signals from utilities, and thelike.

According to some embodiments, demand response layer 414 includescontrol logic for responding to the data and signals it receives. Theseresponses can include communicating with the control algorithms inintegrated control layer 418, changing control strategies, changingsetpoints, or activating/deactivating building equipment or subsystemsin a controlled manner. Demand response layer 414 may also includecontrol logic configured to determine when to utilize stored energy. Forexample, demand response layer 414 may determine to begin using energyfrom energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control moduleconfigured to actively initiate control actions (e.g., automaticallychanging setpoints) which minimize energy costs based on one or moreinputs representative of or based on demand (e.g., price, a curtailmentsignal, a demand level, etc.). In some embodiments, demand responselayer 414 uses equipment models to determine an optimal set of controlactions. The equipment models can include, for example, thermodynamicmodels describing the inputs, outputs, and/or functions performed byvarious sets of building equipment. Equipment models may representcollections of building equipment (e.g., subplants, chiller arrays,etc.) or individual devices (e.g., individual chillers, heaters, pumps,etc.).

Demand response layer 414 may further include or draw upon one or moredemand response policy definitions (e.g., databases, XML files, etc.).The policy definitions can be edited or adjusted by a user (e.g., via agraphical user interface) so that the control actions initiated inresponse to demand inputs can be tailored for the user's application,desired comfort level, particular building equipment, or based on otherconcerns. For example, the demand response policy definitions canspecify which equipment can be turned on or off in response toparticular demand inputs, how long a system or piece of equipment shouldbe turned off, what setpoints can be changed, what the allowable setpoint adjustment range is, how long to hold a high demand setpointbefore returning to a normally scheduled setpoint, how close to approachcapacity limits, which equipment modes to utilize, the energy transferrates (e.g., the maximum rate, an alarm rate, other rate boundaryinformation, etc.) into and out of energy storage devices (e.g., thermalstorage tanks, battery banks, etc.), and when to dispatch on-sitegeneration of energy (e.g., via fuel cells, a motor generator set,etc.).

Integrated control layer 418 can be configured to use the data input oroutput of building subsystem integration layer 420 and/or demandresponse later 414 to make control decisions. Due to the subsystemintegration provided by building subsystem integration layer 420,integrated control layer 418 can integrate control activities of thesubsystems 428 such that the subsystems 428 behave as a singleintegrated supersystem. In some embodiments, integrated control layer418 includes control logic that uses inputs and outputs from a pluralityof building subsystems to provide greater comfort and energy savingsrelative to the comfort and energy savings that separate subsystemscould provide alone. For example, integrated control layer 418 can beconfigured to use an input from a first subsystem to make anenergy-saving control decision for a second subsystem. Results of thesedecisions can be communicated back to building subsystem integrationlayer 420.

Integrated control layer 418 is shown to be logically below demandresponse layer 414. Integrated control layer 418 can be configured toenhance the effectiveness of demand response layer 414 by enablingbuilding subsystems 428 and their respective control loops to becontrolled in coordination with demand response layer 414. Thisconfiguration may advantageously reduce disruptive demand responsebehavior relative to conventional systems. For example, integratedcontrol layer 418 can be configured to assure that a demandresponse-driven upward adjustment to the setpoint for chilled watertemperature (or another component that directly or indirectly affectstemperature) does not result in an increase in fan energy (or otherenergy used to cool a space) that would result in greater total buildingenergy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback todemand response layer 414 so that demand response layer 414 checks thatconstraints (e.g., temperature, lighting levels, etc.) are properlymaintained even while demanded load shedding is in progress. Theconstraints may also include setpoint or sensed boundaries relating tosafety, equipment operating limits and performance, comfort, fire codes,electrical codes, energy codes, and the like. Integrated control layer418 is also logically below fault detection and diagnostics layer 416and automated measurement and validation layer 412. Integrated controllayer 418 can be configured to provide calculated inputs (e.g.,aggregations) to these higher levels based on outputs from more than onebuilding subsystem.

Automated measurement and validation (AM&V) layer 412 can be configuredto verify whether control strategies commanded by integrated controllayer 418 or demand response layer 414 are working properly (e.g., usingdata aggregated by AM&V layer 412, integrated control layer 418,building subsystem integration layer 420, FDD layer 416, or otherwise).The calculations made by AM&V layer 412 can be based on building systemenergy models and/or equipment models for individual BMS devices orsubsystems. For example, AM&V layer 412 may compare a model-predictedoutput with an actual output from building subsystems 428 to determinean accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured toprovide on-going fault detection for building subsystems 428, buildingsubsystem devices (i.e., building equipment), and control algorithmsused by demand response layer 414 and integrated control layer 418. FDDlayer 416 may receive data inputs from integrated control layer 418,directly from one or more building subsystems or devices, or fromanother data source. FDD layer 416 may automatically diagnose andrespond to detected faults. The responses to detected or diagnosedfaults can include providing an alert message to a user, a maintenancescheduling system, or a control algorithm configured to attempt torepair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification ofthe faulty component or cause of the fault (e.g., loose damper linkage)using detailed subsystem inputs available at building subsystemintegration layer 420. In other exemplary embodiments, FDD layer 416 isconfigured to provide “fault” events to integrated control layer 418which executes control strategies and policies in response to thereceived fault events. According to some embodiments, FDD layer 416 (ora policy executed by an integrated control engine or business rulesengine) may shut-down systems or direct control activities around faultydevices or systems to reduce energy waste, extend equipment life, orassure proper control response.

FDD layer 416 can be configured to store or access a variety ofdifferent system data stores (or data points for live data). FDD layer416 may use some content of the data stores to identify faults at theequipment level (e.g., specific chiller, specific AHU, specific terminalunit, etc.) and other content to identify faults at component orsubsystem levels. For example, building subsystems 428 may generatetemporal (i.e., time-series) data indicating the performance of BMS 400and the various components thereof. The data generated by buildingsubsystems 428 can include measured or calculated values that exhibitstatistical characteristics and provide information about how thecorresponding system or process (e.g., a temperature control process, aflow control process, etc.) is performing in terms of error from itssetpoint. These processes can be examined by FDD layer 416 to exposewhen the system begins to degrade in performance and alert a user torepair the fault before it becomes more severe.

Referring now to FIG. 5, a block diagram of another building managementsystem (BMS) 500 is shown, according to some embodiments. BMS 500 can beused to monitor and control the devices of HVAC system 100, watersidesystem 200, airside system 300, building subsystems 428, as well asother types of BMS devices (e.g., lighting equipment, securityequipment, etc.) and/or HVAC equipment.

BMS 500 provides a system architecture that facilitates automaticequipment discovery and equipment model distribution. Equipmentdiscovery can occur on multiple levels of BMS 500 across multipledifferent communications busses (e.g., a system bus 554, zone buses556-560 and 564, sensor/actuator bus 566, etc.) and across multipledifferent communications protocols. In some embodiments, equipmentdiscovery is accomplished using active node tables, which provide statusinformation for devices connected to each communications bus. Forexample, each communications bus can be monitored for new devices bymonitoring the corresponding active node table for new nodes. When a newdevice is detected, BMS 500 can begin interacting with the new device(e.g., sending control signals, using data from the device) without userinteraction.

Some devices in BMS 500 present themselves to the network usingequipment models. An equipment model defines equipment objectattributes, view definitions, schedules, trends, and the associatedBACnet value objects (e.g., analog value, binary value, multistatevalue, etc.) that are used for integration with other systems. Somedevices in BMS 500 store their own equipment models. Other devices inBMS 500 have equipment models stored externally (e.g., within otherdevices). For example, a zone coordinator 508 can store the equipmentmodel for a bypass damper 528. In some embodiments, zone coordinator 508automatically creates the equipment model for bypass damper 528 or otherdevices on zone bus 558. Other zone coordinators can also createequipment models for devices connected to their zone busses. Theequipment model for a device can be created automatically based on thetypes of data points exposed by the device on the zone bus, device type,and/or other device attributes. Several examples of automatic equipmentdiscovery and equipment model distribution are discussed in greaterdetail below.

Still referring to FIG. 5, BMS 500 is shown to include a system manager502; several zone coordinators 506, 508, 510 and 518; and several zonecontrollers 524, 530, 532, 536, 548, and 550. System manager 502 canmonitor data points in BMS 500 and report monitored variables to variousmonitoring and/or control applications. System manager 502 cancommunicate with client devices 504 (e.g., user devices, desktopcomputers, laptop computers, mobile devices, etc.) via a datacommunications link 574 (e.g., BACnet IP, Ethernet, wired or wirelesscommunications, etc.). System manager 502 can provide a user interfaceto client devices 504 via data communications link 574. The userinterface may allow users to monitor and/or control BMS 500 via clientdevices 504.

In some embodiments, system manager 502 is connected with zonecoordinators 506-510 and 518 via a system bus 554. System manager 502can be configured to communicate with zone coordinators 506-510 and 518via system bus 554 using a master-slave token passing (MSTP) protocol orany other communications protocol. System bus 554 can also connectsystem manager 502 with other devices such as a constant volume (CV)rooftop unit (RTU) 512, an input/output module (IOM) 514, a thermostatcontroller 516 (e.g., a TEC5000 series thermostat controller), and anetwork automation engine (NAE) or third-party controller 520. RTU 512can be configured to communicate directly with system manager 502 andcan be connected directly to system bus 554. Other RTUs can communicatewith system manager 502 via an intermediate device. For example, a wiredinput 562 can connect a third-party RTU 542 to thermostat controller516, which connects to system bus 554.

System manager 502 can provide a user interface for any devicecontaining an equipment model. Devices such as zone coordinators 506-510and 518 and thermostat controller 516 can provide their equipment modelsto system manager 502 via system bus 554. In some embodiments, systemmanager 502 automatically creates equipment models for connected devicesthat do not contain an equipment model (e.g., IOM 514, third partycontroller 520, etc.). For example, system manager 502 can create anequipment model for any device that responds to a device tree request.The equipment models created by system manager 502 can be stored withinsystem manager 502. System manager 502 can then provide a user interfacefor devices that do not contain their own equipment models using theequipment models created by system manager 502. In some embodiments,system manager 502 stores a view definition for each type of equipmentconnected via system bus 554 and uses the stored view definition togenerate a user interface for the equipment.

Each zone coordinator 506-510 and 518 can be connected with one or moreof zone controllers 524, 530-532, 536, and 548-550 via zone buses 556,558, 560, and 564. Zone coordinators 506-510 and 518 can communicatewith zone controllers 524, 530-532, 536, and 548-550 via zone busses556-560 and 564 using a MSTP protocol or any other communicationsprotocol. Zone busses 556-560 and 564 can also connect zone coordinators506-510 and 518 with other types of devices such as variable air volume(VAV) RTUs 522 and 540, changeover bypass (COBP) RTUs 526 and 552,bypass dampers 528 and 546, and PEAK controllers 534 and 544.

Zone coordinators 506-510 and 518 can be configured to monitor andcommand various zoning systems. In some embodiments, each zonecoordinator 506-510 and 518 monitors and commands a separate zoningsystem and is connected to the zoning system via a separate zone bus.For example, zone coordinator 506 can be connected to VAV RTU 522 andzone controller 524 via zone bus 556. Zone coordinator 508 can beconnected to COBP RTU 526, bypass damper 528, COBP zone controller 530,and VAV zone controller 532 via zone bus 558. Zone coordinator 510 canbe connected to PEAK controller 534 and VAV zone controller 536 via zonebus 560. Zone coordinator 518 can be connected to PEAK controller 544,bypass damper 546, COBP zone controller 548, and VAV zone controller 550via zone bus 564.

A single model of zone coordinator 506-510 and 518 can be configured tohandle multiple different types of zoning systems (e.g., a VAV zoningsystem, a COBP zoning system, etc.). Each zoning system can include aRTU, one or more zone controllers, and/or a bypass damper. For example,zone coordinators 506 and 510 are shown as Verasys VAV engines (VVEs)connected to VAV RTUs 522 and 540, respectively. Zone coordinator 506 isconnected directly to VAV RTU 522 via zone bus 556, whereas zonecoordinator 510 is connected to a third-party VAV RTU 540 via a wiredinput 568 provided to PEAK controller 534. Zone coordinators 508 and 518are shown as Verasys COBP engines (VCEs) connected to COBP RTUs 526 and552, respectively. Zone coordinator 508 is connected directly to COBPRTU 526 via zone bus 558, whereas zone coordinator 518 is connected to athird-party COBP RTU 552 via a wired input 570 provided to PEAKcontroller 544.

Zone controllers 524, 530-532, 536, and 548-550 can communicate withindividual BMS devices (e.g., sensors, actuators, etc.) viasensor/actuator (SA) busses. For example, VAV zone controller 536 isshown connected to networked sensors 538 via SA bus 566. Zone controller536 can communicate with networked sensors 538 using a MSTP protocol orany other communications protocol. Although only one SA bus 566 is shownin FIG. 5, it should be understood that each zone controller 524,530-532, 536, and 548-550 can be connected to a different SA bus. EachSA bus can connect a zone controller with various sensors (e.g.,temperature sensors, humidity sensors, pressure sensors, light sensors,occupancy sensors, etc.), actuators (e.g., damper actuators, valveactuators, etc.) and/or other types of controllable equipment (e.g.,chillers, heaters, fans, pumps, etc.).

Each zone controller 524, 530-532, 536, and 548-550 can be configured tomonitor and control a different building zone. Zone controllers 524,530-532, 536, and 548-550 can use the inputs and outputs provided viatheir SA busses to monitor and control various building zones. Forexample, a zone controller 536 can use a temperature input received fromnetworked sensors 538 via SA bus 566 (e.g., a measured temperature of abuilding zone) as feedback in a temperature control algorithm. Zonecontrollers 524, 530-532, 536, and 548-550 can use various types ofcontrol algorithms (e.g., state-based algorithms, extremum seekingcontrol (ESC) algorithms, proportional-integral (PI) control algorithms,proportional-integral-derivative (PID) control algorithms, modelpredictive control (MPC) algorithms, feedback control algorithms, etc.)to control a variable state or condition (e.g., temperature, humidity,airflow, lighting, etc.) in or around building 10.

Automatic Tagging

Referring now to FIGS. 6-14, systems and methods for automatic taggingof entities within a building management system (BMS) are shown,according to some embodiments. In some embodiments, an “entity” mayrefer to any unit within a BMS that corresponds to data. In someembodiments, for example, entities may include spaces, equipment,sensors, devices, and points.

In some embodiments of the present disclosure, a computing system isconfigured to organize and associate tags with devices and points.Additionally, in some embodiments the computing system is configured toallow modification of tags that are associated with particular devicesand points, based on the specific configuration that is desired.Embodiments of the computing system disclosed herein can be configuredto add tags to devices and points when a standard field device is addedto the station via the already existing import software or from apalette. In some embodiments, a “tag” may refer to a value to abstractequipment, spaces, and other entities of a BMS. For example, a tag mayindicate an equipment type, point types used or provided by thatequipment type, control relationships between point types and/or anyother attributes common to that type of equipment, to name a few.

Further, embodiments of the computing system can be configured to addtags to devices and points that already exist in a station. In someembodiments, various device categories may be handled, including astandard field device that was originally added to the station withimport, a standard field device that was not originally added withimport, but was later added by hand or by station discovery, and anon-standard field device. In some situations, a standard field devicemay refer to a Johnson Controls field device, whereas a non-standardfield device may refer to a field device not associated with JohnsonControls.

The automatic tagging of the present disclosure may include addingappropriate direct tags/tag groups as defined in a system library to adevice, as well as adding appropriate direct tags/tag groups as definedin the system library to points. The automatic tagging may furtherprovide that when devices are added via a palette (see, e.g., a JohnsonControls TEC3000, electric meters) then tags can be added to the devicesand points also utilizing the system library.

Referring now to FIG. 6, a block diagram showing a computing system 600is shown, according to one embodiment. Computing system 600 can be acomputing system or controller of the building management systems (BMS)described above with respect to FIGS. 1-5. Computing system 600 is shownto include a communications interface 604 and a processing circuit 606.Communications interface 604 may include wired or wireless interfaces(e.g., jacks, antennas, transmitters, receivers, transceivers, wireterminals, etc.) for conducting data communications with varioussystems, devices, or networks. For example, communications interface 604may include an Ethernet card and port for sending and receiving data viaan Ethernet-based communications network and/or a WiFi transceiver forcommunicating via a wireless communications network. Communicationsinterface 604 may be configured to communicate via local area networksor wide area networks (e.g., the Internet, a building WAN, etc.) and mayuse a variety of communications protocols (e.g., BACnet, IP, LON, etc.).

Communications interface 604 may be a network interface configured tofacilitate electronic data communications between computing system 600and various external systems or devices (e.g., user interface 634,device 636). Computing system 600 may receive tag update commands fromuser interface 634 and device information (e.g., an indication that anew device has been added) from device 636. Computing system 600 may beconfigured to output user input requests to user interface 634.

Processing circuit 606 is shown to include a processor 608 and memory610. Processor 608 may be a general purpose or specific purposeprocessor, an application specific integrated circuit (ASIC), one ormore field programmable gate arrays (FPGAs), a group of processingcomponents, or other suitable processing components. Processor 608 maybe configured to execute computer code or instructions stored in memory610 or received from other computer readable media (e.g., CDROM, networkstorage, a remote server, etc.).

Memory 610 may include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 610 may include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory610 may include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 610 may be communicably connected toprocessor 608 via processing circuit 606 and may include computer codefor executing (e.g., by processor 608) one or more processes describedherein.

In some embodiments, computing system 600 includes a system library 624containing data as described herein, which can be run by software coderegardless of whether the automatic tagging is done on import orthereafter. In some embodiments, the construction of the system library624 can be enhanced for system library files to explicitly list theappropriate tags for the device and the points. For example, a “SystemLibrary Editor” and an existing spreadsheet that creates SystemLibraries can be enhanced to support the addition/modification/deletionof tagging data. In some situations, system library files can includePCT files (e.g., files corresponding to a programmable controller toolsuch as FX-PCT and FC-PCT) and/or WT4000 files (e.g., filescorresponding to a BACnet device). The system library 624 can supportadding tags at the device and at a point. The tags can be individualtags or tag groups.

In some embodiments of the present disclosure, systems and methods ofautomatic tagging of devices and points are configured using the Niagarasoftware platform (e.g., Niagara 4). Accordingly, tags can be of theform “namespace:tag” where the namespace is the nickname used withinNiagara to identify the tag dictionary. For example, “n:point” refers tothe point tag in the Niagara tag dictionary. If the tag is a value tag,then the value is provided using an equal's sign. For example,“hs:stage=2” refers to the stage value tag in a Haystack tag dictionaryand assigns it a value of 2. If multiple tags are to be assigned, theycan be separated by a semicolon (“e.g., “hs:damper;hs:cmd”). Tag groupscan also be supported. In some embodiments, the system library does notdifferentiate between tag groups and tags, so a tag group can beindicated as “namespace:taggroup” (e.g., “hs:zoneAirTemperatureSensor”).

An enhanced system library header can contain any tags that should beadded to the device by adding the tags xml attribute. In someembodiments, if this attribute is not present or has a blank value thenno tags will be added. The non-limiting example tables below describethe details of the construction of FX system libraries, according to anexample embodiment. The elements specific to automatic tagging are shownin bold.

TABLE 1 Structure of System Library Header - CAF File Import Field NameDescription Example Default Description Description of the FanCoil- Nonesystem library. Zoning Author Author of the system library Milw NonePCTVersion Version of PCT that was used to 10.1 None construct thesystem library - in particular this is important for the BACoids used toidentify the points. Date Date of the system library. Jan. 18, 2019 None

Table 1 describes the fields for an application supported by a PCTsystem library. In this example, all of the fields are xml attributes.

TABLE 2 Structure of System Library for Point - CAF File Import FieldName Description Example Default BACoid Unique Identifier of Object inthe CAF 2045 None file. The value −1 may be used to tag the device.Import Flag (Y/N) to indicate if Object should N be importedPCTPointName Name of Object in CAF file SF-C None FXName Name of ControlPoint in FX Supervisor SF-C None Database PointOrder Integer used toorder points in FX 10000 Supervisor Database. Lowest number of importedobjects appears first. Tags List of zero, one or more tags thaths:fan;hs:cmd Blank should be associated with the device or point. Ifblank, no tags. Each tag of the format namespace:tagname, or, if using atag group, namespace:tagegroupname. If multiple tags are needed, theyare separated by semicolons. If a value tag, the format isnamespace:tagname=value. ExportTag {Future} Flag (Y/N) to indicate if NControl Point should be tagged for FX Server export in the FX SupervisorDatabase. Condition1 A Bacoid. Used (along with Condition2) Empty toconditionally import an object from a CAF file, if the Import flag istrue. An empty value means import is unconditional. Multiple BACoidsseparated by commas are OR conditions. So 1234, 5678 means condition1will be true if either BACoid 1234 or 5678 is in the CAF file.Condition2 A Bacoid. Used (along with Condition1) Empty to conditionallyimport an object from a CAF file, if the Import flag is true. An emptyvalue means import is unconditional. Multiple BACoids separated bycommas are OR conditions. So 1234, 5678 means condition1 will be true ifeither BACoid 1234 or 5678 is in the CAF file. Extensions/ScheduleLegacy. None Extensions/Totalization A flag (Y/N) to indicate if atotalization N extension should be added to the point in the FXSupervisor database. Extensions/Alarm A flag (Y/N) to indicate if analarm N extension should be added to the point in the FX Supervisordatabase Extensions/Trend/Interval A flag (Y/N) to indicate if aninterval N trend extension should be added to the point in the FXSupervisor database Extensions/Trend/Interval_Time Time, in minutes, forthe interval trend.   15 Only applicable if the Interval field value isT. Extensions/Trend/COV A flag (Y/N) to indicate if a COV trend Nextension should be added to the point in the FX Supervisor databaseExtensions/Trend/COV_Tolerence Tolerance for COV trend. Only   1applicable if the COV field value is T. Extensions/Alarm/. . . {Future}

Table 2 describes the fields for each Object in a PCT system library. Inthis example, all of the fields are xml attributes.

TABLE 3 Structure of System Library Header - WT4000 CSV File ImportField Name Description Example Default Description Description of theWireless None system library. Pneumatic Stat Author Author of the systemMilw None library WT4000Version Version of WT4000 tools 1.0 None thatwere used to construct the system library - in particular this isimportant for the Modbus register values used to identify the points.Date Date of the system library. Jan. 18, 2019 None

Table 3 describes the fields for the application supported by a WT4000system library. In this example, all of the fields are xml attributes.

TABLE 4 Structure of System Library for Point - WT4000 CSV File ImportField Name Description Example Default ModbusRegister An integer used toidentify the point in 57 None the thermostat. This value, and,optionally, either Byte or Bit, serves to address the point in thethermostat. To tag devices the following special values may be used:5000 - a gateway device 5159 - a MFM device 5145 - a MFR device 5161 - aMCR device 5160 - a MCM device Byte Optional. Either H or L or blank. IfH Blank blank, it is not used to address the point in the thermostat. IfH, refers to the high order byte in the Modbus register, if L the loworder byte in the Modbus Register. Bit Optional. Either blank or twodigits used 01 Blank to identify the bit in a register. If blank, it isnot used to address the point in the thermostat. Otherwise, 00 is bit 0,01 is bit 1 etc. Import Flag (Y/N) to indicate if Object should N beimported ConfigToolName Name of the point in the import file, withWT_4000_xxx_ai_57 None xxx used instead of the thermostat model numberFXName String to be used as the name of the point ZN-T None in FXSupervisor. FXDesc String to be used as the description of the Zone Nonepoint in FX Supervisor. Temperature PointOrder Integer used to orderpoints in FX 10000 Supervisor Database. Lowest number of importedobjects appears first. Tags List of zero, one or more tags thaths:zone;hs:air; Blank should be associated with the device orhs:temp;hs:sensor point. If blank, no tags. Each tag of the formatnamespace:tagname, or, if using a tag group, namespace:tagegroupname. Ifmultiple tags are needed, they are separated by semicolons. If a valuetag, the format is namespace:tagname=value. ExportTag {Future} Flag(Y/N) to indicate if N Control Point should be tagged for FX Serverexport in the FX Supervisor Database. Condition1 A string to indicate ifthe point should be Empty imported, if a point at this address exists ornot in the import file. Condition2 A string to indicate if the pointshould be Empty imported, if a point at this address exists or not inthe import file. Extensions/Schedule Not used, legacy. NoneExtensions/Totalization A flag (Y/N) to indicate if a totalization Nextension should be added to the point in the FX Supervisor database.Extensions/Alarm A flag (Y/N) to indicate if an alarm N extension shouldbe added to the point in the FX Supervisor databaseExtensions/Trend/Interval A flag (Y/N) to indicate if an interval Ntrend extension should be added to the point in the FX Supervisordatabase Extensions/Trend/Interval_Time Time, in minutes, for theinterval trend. 15 Only applicable if the Interval field value is T.Extensions/Trend/COV A flag (Y/N) to indicate if a COV trend N extensionshould be added to the point in the FX Supervisor databaseExtensions/Trend/COV_Tolerence Tolerance for COV trend. Only  1applicable if the COV field value is T. Extensions/Alarm/. . . {Future}

Table 4 describes the fields for each Object in a WT4000 system library.In this example, all of the fields are xml attributes.

Still referring to FIG. 6, computing system 600 is shown to include animport module 612. Import module 612 may be used to automatically tagdevices and/or points upon file import. Import module 612 is shown incommunication with user interface 634. Additionally, import module 612is shown in communication with device 636. User interface 634 may beused to provide information to import module 612, such as taginformation and/or device information. Import module 612 may communicatewith user interface 634 to request additional input data from a user.

Similarly, computing system 600 is shown to include an update module626. Update module 626 may be used to automatically update devicesand/or points upon request (e.g., by a user). Update module 626 is shownin communication with user interface 634. Additionally, update module626 is shown in communication with device 636. User interface 634 may beused to provide information to update module 626, such as a request toupdate tags. Update module 626 may communicate with user interface 634to request additional input data from a user.

Import module 612 is shown to include an identification module 614, aparsing module 616, a verification module 618, a tag type module 620,and a tag addition module 622. Further, import module 612 maycommunicate with the system library 624. Identification module 614 maybe used to identify a point or device (e.g., device 636), upon import,that can be tagged. Import module 612 may then communicate with systemlibrary 624 to determine any associated tags of the point or device.Parsing module 616 may detect if a string is in the tag attribute, andmay then parse the string to process each tag, one at a time. For eachtag, the indicated tag dictionary may be checked for the existence andtype of the tag (e.g., marker, value, or tag group).

In some embodiments, the verification module 618 may then check to seeif the tag is valid for that point (e.g., if the tag is already present,it is not added again). If the tag is valid, then tag type module 620may interrogate the type to determine how to add the tag. If, forexample, the tag is a marker or tag group, then tag addition module 622may simply add the tag to the device or point. However, if the tag is avalue tag, for example, it may be added to the device or point and thevalue may be specified in the library that is associated with the tag.

Update module 626 is shown to include a library determination module628, a tag type module 630, and a tag addition module 632. Further,update module 626 may communicate with system library 624. Librarydetermination module 628 may be used to determine what, if any, librarywas used upon import for the specific point or device. Update module 626may communicate with a library (in some cases, system library 624) todetermine any associated tags of the point or device. Next, tag typemodule 620 may interrogate the type to determine how to add the tag. If,for example, the tag is a marker or tag group, then tag addition module622 may simply add the tag to the device or point. However, if the tagis a value tag, for example, it may be added to the device or point andthe value may be specified in the library that is associated with thetag.

Referring now to FIG. 7, a flow chart of a method 700 for automatictagging is shown, according to an example embodiment. In someembodiments, the method 700 is performed by computing system 600.Alternatively, the automatic tagging method 700 may be partially orcompletely performed by another computing system or controller. Method700 is shown to include determining an occurrence of a tagging event(step 702). In some embodiments, the tagging event may correspond to anew device or point file import. Additionally, in some embodiments, thetagging event may correspond to a user request to update existing deviceor point tags. The user request may occur via a user interface, asdescribed above. Alternatively, the tagging event may correspond to adifferent controller input.

Method 700 is shown to include identifying a point or devicecorresponding to the tagging event (step 704). In some embodiments, theidentification may include locating a point or device ID, for example,in a corresponding library. In some situations, the correspondinglibrary may be the system library. Next, method 700 is shown to includedetermining tags associated with the point or device (step 706). In someembodiments, the determination may include using stored library tags.Method 700 is shown to include verifying tag data and the associationwith the point or device (step 708). This may include checking the pointto see if the tag is valid for that point. As one non-limiting example,if a tag is already present, then it will not be added again.

Additionally, method 700 is shown to include determining the tag type(step 710). In some embodiments, the tag type can determine how to addthe tag to the point or device. As one non-limiting example, the tag maybe a marker, tag group, or value tag. Next, method 700 is shown toinclude adding the tag to the point or device using the tag type (step712). In one example, if the tag is a marker or tag group, it may besimply added to the point or device. As another example, if the tag is avalue tag, it may be added to the point or device and the valuespecified in the library may be associated with the tag.

In some embodiments, the method of automatically tagging upon import maybe done either when the points are added to a device on import of CAFfiles (e.g., either BACnet or N2) and CSV files for BACnet WT 4000, oron demand on a per device basis using a user interface (e.g., a tabularuser interface). In either case, the tags may be held in the systemlibrary. In the case of import, the tags may be applied along with otherlibrary information at the time of import. When adding tags to a deviceand its points that already exist on a station, the library may also beused.

Before any parsing of the file takes place, the station may be checkedby the tag dictionary service. If it is not present, then tags may notbe added. In some embodiments, tags can be added to control pointsand/or the device.

Referring now to FIG. 8, a flow chart of a method 800 for automatictagging is shown according to an example embodiment. In someembodiments, the method 800 may be performed by the computing system600. Alternatively, the automatic tagging method 800 may be partially orcompletely performed by another computing system or a controller.

Method 800 is shown to include determining an occurrence of a taggingevent (step 802). In some embodiments, the tagging event may correspondto a new device or point file import. Additionally, in some embodiments,the tagging event may correspond to a user request to update existingdevice or point tags. The user request may occur via a user interface,as described above. Alternatively, the tagging event may correspond to adifferent controller input.

Method 800 is shown to include retrieving tags from the system library(step 804). In some embodiments, this may include identifying a point ordevice corresponding to the tagging event, and using the system libraryto look up or retrieve corresponding tags. Next, method 800 is shown toinclude parsing the tag list (step 806). In some embodiments, if thereis a string in the tags attribute, then the string may be parsed toprocess each tag, one at a time.

Additionally, method 800 is shown to include verifying that the tag ortag group exists in the indicated dictionary (step 808). In someembodiments, this may include checking for the type of the tag (e.g.,marker, value, or tag group). Method 800 is shown to include verifyingthat the point or device can be tagged with the tag or tag group (e.g.,the point or device is checked to see if the tag or tag group is validfor that point) (step 810). Next, method 800 is shown to include addingthe tag or tag group to the point or device (step 812). The addition ofthe tag or tag group may be carried out using a plurality of methods. Insome embodiments, the methods of adding the tag or tag group may bebased on the type of the tag or tag group.

Referring now to FIG. 9, a flow chart of a method 900 for automatictagging upon import is shown, according to an example embodiment. Insome embodiments, the method 900 is performed by the computing system600. Alternatively, the method 900 may be partially or completelyperformed by a different computing system or controller. The method 900is shown to include determining if a tag dictionary is present (step902). If the tag dictionary is not present (i.e., the result of step 902is “no”), method 900 ends. Alternatively, if the tag dictionary ispresent (i.e., the result of step 902 is “yes”), a point or device maythen be located within the system library (step 904).

Method 900 is shown to include determining if the point or device shouldbe added to the station (step 906). If the point or device should not beadded to the station (i.e., the result of step 906 is “no”), method 900ends. Alternatively, if the point or device should be added to thestation (i.e., the result of step 906 is “yes”), the system library maybe checked for associated tags (step 908). Method 900 may then determineif the tag attribute contains a string (step 910). If the tag attributecontains a string (i.e., the result of step 910 is “yes”), the stringmay be parsed to process each tag (step 912), prior to checking the tagdictionary corresponding to the tag for the existence and type of thetag (step 914). If the tag attribute does not contain a string (i.e.,the result of step 910 is “no”), then method 900 may include checkingthe tag dictionary corresponding to the tag for the existence and typeof the tag (step 914).

Method 900 is shown to include determining if the tag is valid for thepoint or device (step 916). If the tag is not valid for the point ordevice (i.e., the result of step 916 is “no”), method 900 may end.Alternatively, if the tag is valid for the point or device (i.e., theresult of step 916 is “yes”), the tag type may then be interrogated todetermine a method for adding the tag (step 918). Next, method 900 mayinclude determining if the tag is a “value” tag type (step 920). If thetag type is a value tag (i.e., the result of step 920 is “yes”), the tagmay be added to the point or device and a specific value may beassociated with the tag (step 924). If the tag type is not a value tag(i.e., the result of step 920 is “no”), the tag may be added to thepoint or device (step 922).

In some embodiments, existing devices may be automatically tagged.Similar to the tagging on import functionality, the tags themselves maybe associated with devices and points in a system library. The decisionsinvolved may include determining how the appropriate system library isselected and how the tags and points in the station are matched.

Referring now to FIG. 10, a flow chart of a method 1000 for updatingexisting points and/or devices is shown, according to an exampleembodiment. Method 1000 may be performed by computing system 600.Alternatively, method 1000 may be partially or completely performed byanother computing system or controller. The method 1000 is shown toinclude interrogating a device to determine if a library was used atimport (step 1002). If a library is present (i.e., the result of step1004 is “yes”), then tags that are associated with the device may beretrieved from the library (step 1012). If a library is not present(i.e., the result of step 1004 is “no”), then it may be determined if asystem type is present (step 1006). If a system type is present (i.e.,the result of step 1006 is “yes”), then the system may be mapped to asystem library (step 1008). Next, method 1000 may include retrieving thetags associated with the device from the system library (step 1012). Ifa system type is not present (i.e., the result of step 1006 is “no”),then the user may be prompted to select a library (step 1010) prior toretrieving tags associated with the device (step 1012). Once tags havebeen retrieved that are associated with the device (step 1012), method1000 may include adding the tags to the device (step 1014).

In some embodiments, if the device is a BACnet device, then the BACnetpoint instance numbers may be used to find the point in the library. Insome embodiments, tags associated with the first match may be retrievedand added to the point—since the original resource file that wasimported is not known, the conditions within the file may not beapplied.

In some embodiments, if the device is not a BACnet device, then thedisplay name of the point in the station may be compared against theFXName in the system library. In some embodiments, when they are equal,any tags may be applied. Just as with the BACnet points, the first matchmay be used.

Referring now to FIGS. 11-13, several example user interfaces are shown,according to an example embodiment. As shown by FIG. 11, a userinterface 1100 of a manager may support tagging activities at the devicelevel for devices that exist in the station. The manager may display atable of all of the devices in the station. In some embodiments, theuser interface 1100 is configured to allow a user to select all devicesusing a button or select devices individually in the table. A Clear Allbutton may deselect all selections. A selected device 1102 (e.g.,“custom2”) is shown as corresponding to a tag library field 1104 (e.g.,“PCT-Custom”).

In some embodiments, when one or more devices are selected, the userinterface 1100 is configured to allow the user to add or remove tagsfrom the devices and the control points they contain. In someembodiments, the Add Tags button may add tags to the devices and pointsand the Remove Tags button may remove the tags. In some embodiments, theRemove Tags button may not remove the implied tags that a softwarepackage (e.g., Niagara) automatically associates with various entities.

Referring to FIG. 12, a user interface 1200 of the system library editormay be configured to allow for adding of tags for system libraries thatapply to PCT/CCT caf and WT4000 csv file import, for example. In someembodiments, PCT files may correspond to a programmable controller tool.In some embodiments, CCT files may correspond to a controllerconfiguration tool. Further, in some embodiments, WT4000 files maycorrespond to a BACnet device. In some embodiments, an edit box may beadded to the header tab for tags—this may contain any tags that shouldbe applied to the device.

Referring to FIG. 13, a user interface 1300 of the system library showsadding a tags column to the points table and, when a point is selectedfor editing, a tags edit box may allow the user to associate tags withthe point. These updates may apply to editing existing system librariesas well as creating a system library from a caf or a csv file. Theassociated spreadsheet may be enhanced to support adding tags at boththe application and the point level, for example by adding theappropriate named ranges to the spreadsheets and enhancing the macros towrite the tags to the generated system library file.

Example—Testing

The following describes a testing process example, according to someembodiments. In preparation for testing, a user may be prompted toselect one PCT system library and the StatGateway system library withwhich to test the System library editor. In some embodiments, each ofthe selected items have no tags. The user may be promoted to make copiesof each and save them with useful names in the install directory ofNiagara. In some embodiments, the tag free libraries are used to fullytest the system library editor.

In some embodiments, the user may select BACnet and N2 caf files as wellas an original and a new WT4000 csv file for testing tagging on import.The user may add some devices using import with libraries without tagsfor testing the tagging of existing points. In some embodiments, theuser may replace these libraries with the libraries with tags for thetags to be applied. The user may have non-BACnet devices to test the tagmatching by name.

In some embodiments, testing the system library editor may include:

-   -   1. Start the system library editor and select the PCT library        without tags and open it.        -   a. On the Points tab the Tags column for all points may be            blank.    -   2. Save the PCT library without tags using a different file        name.        -   a. Library may have the Tags attribute added to all points            (if not there already) but may not have tags entries.    -   3. Start the system library editor. Select the StatGateway        library without tags and open it.        -   a. On the Points tab the Tags column for all points may be            blank.    -   4. Save the StatGateway library without tags using a different        file name.        -   a. Library may have the Tags attribute added to all points            (if not there already) but no tags entries.    -   5. Start the system library editor. Select a PCT library with        tags and open it.        -   a. On the Points tab the Tags column may contain tags for            some of the points. b. On the Points tab the Tags column may            contain an appropriate tag (e.g., hs:ahu) for BACoid with            value −1, corresponding to the device.    -   6. Save the PCT library with tags using a different file name.        -   a. Library may have the Tags attribute on all points and all            of the tag entries.    -   7. Start the system library editor. Select the StatGateway        library with tags and open it.        -   a. On the Points tab the Tags column may contain tags for            some of the points.        -   b. On the Points tab the Tags column may contain an            appropriate tag (e.g., hs:ahu) for ModbusRegister with value            5000, corresponding to the gateway device.    -   8. Save the StatGateway library with tags using a different file        name.        -   a. Library may have the Tags attribute on the header and all            points and all of the tag entries.    -   9. Start the system library editor. Select the PCT system        library that was saved in part 2 above. Edit the tags field of        one or more points in the library but do not save it.        -   a. Library may not have tags added to points.    -   10. Start the system library editor. Select the PCT system        library that was saved in part 2 above. Edit the tags field of        one or more points in the library and save it. Make a note of        the points and tags that were added. One of the points may have        multiple tags separated by a semicolon.        -   a. Library may have tags added to the points.    -   11. Start the system library editor. Select the StatGateway        system library that was saved in part 4 above. Edit the tags        field of one or more points in the library but do not save it.        -   a. Library may not have tags added to points.    -   12. Start the system library editor. Select the StatGateway        system library that was saved in part 4 above. Edit the tags        field of one or more points in the library and save it. Make a        note of the points and tags that were added. One of the points        may have multiple tags separated by a semicolon.        -   a. Library may have tags added to the points.    -   13. Start the system library editor. Select a caf file to        initially populate a library. Add tag(s) on one or more points        on the point tab. Make a note of the tags that were added. Use        the Save As button to save the library.        -   a. Library may have tags added to the points.    -   14. Start the system library editor. Select an original WT 4000        csv file to initially populate a library. Add tag(s) on one or        more points on the point tab. Make a note of the tags that were        added. Use the Save As button to save the library.        -   a. Library may have tags added to the points.    -   15. Start the system library editor. Select a new WT 4000 csv        file to initially populate a library. Add tag(s) on one or more        points on the point tab. Make a note of the tags that were        added. Use the Save As button to save the library.        -   a. Library may have tags added to the points.

Import Files:

-   -   1. Using the import manager, import a caf file using a system        library that may have tags defined. Verify that tags that are        present in the system library have been added to the device and        appropriate points.    -   2. Using the import manager, import an original WT 4000 csv file        using a system library that has tags defined. Verify that tags        that are present in the system library have been added to the        device and appropriate points.    -   3. Using the import manager, import a new WT 4000 csv file using        a system library that has tags defined. Verify that tags that        are present in the system library have been added to the device        and appropriate points.

4. Run the same tests as in items 1-3 above, only this time use thesystem library files that were edited with the system library editor toadd tags.

Tag Query

In some embodiments, the systems and methods described herein can beused to query tags. In some embodiments, search functionality may becase insensitive. In some embodiments, a case insensitive NEQL searchmay be implemented using Niagara (e.g., Niagara Search API).

Tag Conversion

In some embodiments, the systems and methods described herein can beused to automatically convert tags (e.g., adding or creating secondarytags) using a utility application. In some embodiments, features of theutility application can be implemented once tags have been previouslycreated and/or added to devices, points, or other components within astation. In some embodiments, the new tags are configured or formattedfor an alternate software platform, and/or use a different syntax ascompared to the previously created tags. In some embodiments, thepreviously created tags may correspond to Niagara syntax, and the newtags may correspond to Haystack syntax. Accordingly, the new tags may beused to automate tagging within a separate software environmentcompatible with “Haystack” formats. In some embodiments, a softwareservice may be installed prior to the generation of the new tags.

In some situations, the software service may be the Niagara4 nHaystackService at Version 2.02 or later. In some embodiments, the secondarytagging features may correspond to a utility. The utility may becontained within the jciHaystackUtil.jar file. This JAR file may have apalette with a single component named “haystackUtil” that contains theHaystack Tagging Utility.

In some embodiments, the nHaystack Service may be added to the stations'services. Upon adding this service, the station may be restarted.Alternatively, the user may invoke an “initialize haystack” actioneither from the nHaystack Service or by clicking the “initialize” buttonfrom the “N Haystack Service View.”

Referring now to FIG. 14, a user interface 1400 of a utility configuredfor generating secondary tags (e.g., Haystack tags) from previouslygenerated Niagara tags is shown. User interface 1400 may correspond tothe “FX Haystack Utility.”

The FX Haystack Utility may be utilized after adding direct tags todevices, points, and other components within a station. To run thisUtility, the NHaystackService may be added to the Station andinitialized before running. The “haystackUtil” component found in thejciHaystackUtil palette may be dragged from the palette to somewhereunder the Station's Config node or one of the children of the Confignode.

In some embodiments, when this component runs, a number of processes mayhappen automatically. The utility may check to see if a “site” componenthas already been added. In some embodiments, if there is no “site”component, the utility may automatically add one. It may be added to the“Config” node unless the utility sees a BJciSpaceRoot component and thenit will add the “site” to this BJciSpaceRoot component.

In some embodiments, when the utility sees that the component beingprocessed is a BDevice component, the utility may add the “equip”component to the device. It may also set the “siteRef” tag to point tothe first “site” component found in the station. It may also check thedevice for any direct tags and add those tags to the “equip” haystackvalue.

In some embodiments, the FX Haystack Utility component(BJciHaystackUtility) may have a number of properties that govern howthe component runs. For example, if the user wants to see a trace ofwhat objects and tags are being processed in the application DirectorConsole, the “Trace” property 1402 may be set to true. Setting thisproperty to false may turn off messages other than Exceptions from beingdisplayed in the Application Director Console.

The user may set the property “Add Haystack to Network and Device” 1404to true to process all of the devices and points found in all of thedefined networks. In some embodiments, when this property is set tofalse, then processing of the entire content of the Drivers node may beskipped.

The user may set the property “Add Haystack to Space and Equip” 1406 totrue to process all of the space and equipment objects found in thestation. In some embodiments, when this property is set to false, thenprocessing of the space and equipment objects may be skipped. Herein,“space” may refer to a building, a campus, or other relevant space.

The user may set the property “Add Haystack Starting at Alt Ord” 1408 totrue to process all of the components and the components children foundstarting at a specified ORD. In some embodiments, when this property isset to false, then processing of the specified ORD and its children maybe skipped. This option may be useful when there are components in thestation that are not part of a device, point, space or equipment, butthe components do have direct tags added. This option may also be usefulto process a narrow set of components without going through a large setof components such as setting the ORD to a newly added device. Thisoption may only process the single device and its points and not processthe entire drivers node.

In some embodiments, the user may initiate this utility by selecting(e.g., right-clicking) on the “haystackUtil” component and selecting“Actions\Build Haystack Tags.” When the running of the utility iscomplete, the Status property may be updated as well as the Fault Cause.In some embodiments, if there was an issue, these two properties mayindicate the cause of the error in the Status and Fault Causeproperties. In some embodiments, the utility is configured to include aReset action option that can be invoked to reset all of the component'sproperties to their default value.

In some embodiments, the FX Haystack Utility can be configured to runmultiple times. For example, if direct tags within the Station aremodified after this utility has been run initially, a user may simplyinvoke the “Build Haystack Tags” action and the haystack values may berefreshed with the direct tags found in the selected components.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements can bereversed or otherwise varied and the nature or number of discreteelements or positions can be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepscan be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions can be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure can be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps canbe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed is:
 1. A method for tagging entities in a buildingautomation system (BAS), the method comprising: identifying, by aprocessing circuit, a first entity of one or more entities in a systemlibrary in response to receiving an indication to add the one or moreentities to the BAS, wherein the system library comprises a plurality ofrelationships between a plurality of tags and a plurality of entities;determining, by the processing circuit, one or more tags associated withthe first entity based on the system library; determining, by theprocessing circuit, a tag type for each of the one or more tags based ona tag dictionary; and adding, by the processing circuit, the one or moretags to the first entity based on the tag type of each of the one ormore tags.
 2. The method of claim 1, wherein the method furthercomprises verifying the one or more tags, wherein verifying the one ormore tags comprises comparing the one or more tags to the plurality oftags in the system library.
 3. The method of claim 2, wherein theprocessing circuit omits adding duplicate tags to the first entity basedon the comparison.
 4. The method of claim 1, wherein a user interfaceproduces the indication to add the one or more entities to the BAS. 5.The method of claim 1, wherein the first entity comprises one of aspace, a piece of equipment, a sensor, a device, or a point.
 6. Themethod of claim 1, wherein the tag type is a value tag, wherein thevalue tag further comprises a numeric value associated with the firstentity.
 7. The method of claim 6, wherein the method further comprisesadding, by the processing circuit, the numeric value to the firstentity.
 8. A method for converting tag syntax in a building managementsystem (BMS), the method comprising: receiving, by a processing circuit,a first tag corresponding to a first entity and having a first syntax;identifying, by the processing circuit, a system library associated withthe first entity, wherein the system library comprises a plurality ofrelationships between a plurality of tags and a plurality of entities;and initiating, by the processing circuit, an update process, theprocess comprising: building one or more second tags corresponding tothe first entity and having a second syntax.
 9. The method of claim 8,wherein building the one or more second tags comprises: determining oneor more second tags associated with the first entity based on the systemlibrary; determining a tag type for each of the one or more second tagsbased on a tag dictionary; and adding the one or more second tags to thefirst entity based on a tag type of each of the one or more second tags.10. The method of claim 9, wherein the method further comprisesverifying the one or more second tags, wherein verifying the one or moresecond tags comprises comparing the one or more second tags to theplurality of tags in the system library.
 11. The method of claim 10,wherein duplicate tags are omitted from addition to the first entitybased on the comparison.
 12. The method of claim 9, wherein the firstentity comprises one of a space, a piece of equipment, a sensor, adevice, or a point.
 13. The method of claim 9, wherein the tag type is avalue tag, wherein a value tag further comprises a numeric valueassociated with the first entity.
 14. The method of claim 10, whereinthe method further comprises adding, by the processing circuit, thenumeric value to the first entity.
 15. A building automation systemcomprising: a system library comprising a plurality of relationshipsbetween a plurality of tags and a plurality of entities; a computingsystem coupled to the system library configured to perform a firstimport process and a second update process; wherein the first importprocess associates one or more tags with a first entity; and wherein thesecond update process updates a first tag associated with a secondentity by building one or more second tags.
 16. The building automationsystem of claim 15, wherein the first import process comprises:identifying the first entity in the system library; determining the oneor more tags associated with the first entity based on the systemlibrary; determining a tag type for each of the one or more tags basedon a tag dictionary; and adding the one or more tags to the first entitybased on the tag type of each of the one or more tags.
 17. The buildingautomation system of claim 15, wherein the second update processcomprises: receiving the first tag corresponding to the second entityand having a first syntax; identifying a system type associated with thesecond entity, wherein the system type is associated with the pluralityof relationships in the system library; and building one or more secondtags corresponding to the second entity and having a second syntax. 18.The building automation system of claim 17, wherein building the one ormore second tags comprises: determining the one or more second tagsassociated with the second entity based on the system library;determining a tag type for each of the one or more second tags based ona tag dictionary; and adding the one or more second tags to the secondentity based on the tag type of each of the one or more second tags. 19.The building automation system of claim 18, wherein the tag type is avalue tag, wherein a value tag further comprises a numeric valueassociated with the second entity.
 20. The building automation system ofclaim 15, wherein the first entity comprises one of a space, a piece ofequipment, a sensor, a device, or a point.